Describe your changes

Improved scenario loading time. On real-world example, this change together with other parts of the task managed to reduce loading time by 40-50%.

Changes:

• The scenario graph rendering starts as soon as possible. There is an addition API call at the very beginning. The graph is first fetched without validation, which is very quick. And the rendering starts immediately
• The "tips" and "creator panel" are no longer waiting for the graph to load. They are shown immediately, and their content is added as soon as is possible.

Firefox profiling results on a sample, quite huge scenario:
(profiling started when user sees list of scenarios, then clicks on one of them the chosen scenario is loaded)

• before
  

• after
  

Checklist before merge

• Related issue ID is placed at the beginning of PR title in [brackets] (can be GH issue or Nu Jira issue)
• Code is cleaned from temporary changes and commented out lines
• Parts of the code that are not easy to understand are documented in the code
• Changes are covered by automated tests
• Showcase in dev-application.conf added to demonstrate the feature
• Documentation added or updated
• Added entry in Changelog.md describing the change from the perspective of a public distribution user
• Added MigrationGuide.md entry in the appropriate subcategory if introducing a breaking change
• Verify that PR will be squashed during merge